Repository navigation
Bind recurring billing periods to genuine Order, Payment and Shipment flows - #1182
Conversation
|
|
This source increment is delivered on accepted main Actual-main build 44031867483 passes:
The original main build Default-Maria evidence is explicitly composite: the complete frozen baseline plus the current 17-case Order class covers all 3,455 identities / 34,112 assertions / 39 declared skips, with unchanged shared source and settings. It is not a fresh full-current-head or installed run. All captured local resources remain absent. Both owned topic branches are independently absent remotely and locally; the worktrees are clean and detached. The delivered example binds each period to its genuine original common Order, Payment and physical Shipment under payment-first or grace, with original money timestamps, late acknowledgement, expiry, access, cancellation/future-period and refund fences. Full #1069's 33 customer requirements, remaining physical/partial-stock/fault scenarios, the missing-root startup boundary, installed upgrade/recovery/rollback and publication remain open. No release, #1130 or 2.29 action is selected. |



Recurring billing with a genuine Order now keeps each original period bound to the existing Order, Payment and Shipment routes. Payment-first and grace activation share the common financial states; grace access alone cannot reserve stock or start fulfillment.
The trusted Order-period grant is part of the subject authority. Original admission and its receipt are atomic; replacement bootstrap cannot omit or substitute the policy. Access requires the original timed capture and protected paid publication. A first charge after the cutoff is refused, delayed acknowledgement preserves an on-time commit, late money cannot reactivate access or fulfillment, and physical work retains its separate original budget. Future cancellation fences later periods while current cancellation/recovery selects the original Order and refund. The provider's timing capability and schema are checked before native admission or money dispatch; the existing BillingPeriod payment-descriptor API remains unchanged.
Validation on
504f3cbd:The current PR's bounded MySQL smoke fallback does not include the changed Order class; complete actual-main MySQL/coverage qualification remains required before source delivery acceptance. This source/example increment addresses #1069 PAY-06/SUB-01/SUB-02. The full 33-scenario matrix, fresh-process/installed qualification, missing-root startup boundary and publication remain unfinished. Workflow #1130/2.29 stays held.